5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
- Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-3: Specifying Statements

The Relational Component


The relational component (or relation) includes several abbreviations that correspond to a series of relational operators that are used when comparing the values of two fields, as follows:

LT (less than) checks if the value of a first-named field is less than that of a second field.

GT (greater than) checks if the value of a first-named field is greater than a second field.

LE (less than or equal to)checks if the value of a first-named field is less than or equal to a second field.

GE (greater than or equal to) checks if the value of a first-named field is greater than or equal to a second field.

EQ (equal to)checks if the value of a first-named field is equal to that of a second field.

NE (not equal to) checks if the value of a first-named field is not equal to that of a second field.

IN (includes)checks if a specified character string is included within the value of a field. For example, you could check to see if the letter string NOR is included in the CUSTOMER NAME field.

EX (excludes) checks if a specified character string is excluded from the value of a field. For example, you could check to see if the letter string NOR does not exist in the CUSTOMER NAME field.

Application Design Manual                                         "Powered by Appx Software"

549

©2006 By APPX Software, Inc. All Rights Reserved